NTISthis.com

Evidence Guide: ICTPRG444 - Analyse software requirements

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTPRG444 - Analyse software requirements

What evidence can you provide to prove your understanding of each of the following citeria?

Gather and confirm client requirements

  1. Confirm requirement and scope of project with required personnel
  2. Gather information regarding requirements via sources of information and business processes
  3. Analyse client requirements and problem context and opportunity faced by client
  4. Document client requirements, project scope, related problems and sources of information according to organisational procedures
  5. Submit document to required personnel and seek and respond to feedback
Confirm requirement and scope of project with required personnel

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Gather information regarding requirements via sources of information and business processes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse client requirements and problem context and opportunity faced by client

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document client requirements, project scope, related problems and sources of information according to organisational procedures

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Submit document to required personnel and seek and respond to feedback

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse functional and related non-functional requirements and feasibility of project

  1. Map business processes using modelling tool including unified modelling language (UML)
  2. Determine opportunities in business process efficiencies
  3. Document functional and non-functional processes according to organisational procedures
  4. Analyse technical and operational feasibility of project
  5. Determine budget and schedule feasibility of project
  6. Examine purpose and intent of project within organisation
Map business processes using modelling tool including unified modelling language (UML)

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine opportunities in business process efficiencies

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document functional and non-functional processes according to organisational procedures

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse technical and operational feasibility of project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine budget and schedule feasibility of project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Examine purpose and intent of project within organisation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop high-level system solutions

  1. Develop and document feasible solutions according to client requirements
  2. Explore and document the feasibility of each solution
  3. Examine alternatives against project constraints
  4. Document assumptions, dependencies and required resources
  5. Produce a project risk analysis according to project requirements
  6. Document future requirements according to organisational procedures
Develop and document feasible solutions according to client requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Explore and document the feasibility of each solution

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Examine alternatives against project constraints

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document assumptions, dependencies and required resources

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Produce a project risk analysis according to project requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document future requirements according to organisational procedures

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare and publish software-requirements documentation

  1. Develop software-requirements document according to organisational procedures
  2. Submit software-requirements report to required personnel and obtain project approval
Develop software-requirements document according to organisational procedures

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Submit software-requirements report to required personnel and obtain project approval

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Required Skills and Knowledge

The candidate must demonstrate the ability to complete the tasks outlined in the elements, performance criteria and foundation skills of this unit, including evidence of the ability to:

develop at least two high-level system solutions for one set of software requirements according to client requirements.

In the course of the above, the candidate must:

analysing and document at least two functional and at least two non-functional requirements

document requirements and work performed according to organisational procedures

submit documents and obtain approval.

The candidate must be able to demonstrate knowledge to complete the tasks outlined in the elements, performance criteria and foundation skills of this unit, including knowledge of:

tools and techniques that may be used to analyse software requirements including;

client business domain

content features including clarity and readability

system functionality

document design and usability

budget creation techniques

modelling tools including unified modelling language (UML)

documentation techniques

risk analysis techniques

functions and features, of templates and style guides

the role of stakeholders and the degree of stakeholder involvement

software development life cycle overview

systems development methodologies

organisational procedures.